PR Summary

This pull request includes several changes to the .pipelines/PSResourceGet-Official.yml file, primarily focusing on improving the build and release pipeline for the PSResourceGet module. The most important changes include adding a new release category, modifying the installation and import of the PSResourceGet module, enabling SBOM, and updating the validation and publish jobs.

Pipeline improvements:

• Added a new release category under customTags to categorize the release as NonAzure.
• Enabled SBOM (Software Bill of Materials) generation by setting ob_sdl_sbom_enabled to true.

Module installation and import:

• Removed the installation step for PSResourceGet and replaced it with a direct import of the module, ensuring it is loaded from PSHome. [1] [2]

Validation and publishing updates:

• Updated the drop variable to point to drop_stagebuild_nupkg and added ob_release_environment set to Production.
• Changed the validation job type from agentless to server and added a templateContext for the publish job.

PR Context

PR Checklist

• PR has a meaningful title
  • Use the present tense and imperative mood when describing your changes
• Summarized changes
• Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
• This PR is ready to merge and is not Work in Progress.
  • If the PR is work in progress, please add the prefix WIP: or [ WIP ] to the beginning of the title (the WIP bot will keep its status check at Pending while the prefix is present) and remove the prefix when the PR is ready.
• Breaking changes
  • None
  • OR
  • Documentation needed
    • Issue filed:
• User-facing changes
  • Not Applicable
  • OR
  • Documentation needed
    • Issue filed:
• Testing - New and feature
  • N/A or can only be tested interactively
  • OR
  • Make sure you've added a new test if existing tests do not effectively test the code changed
• Tooling
  • I have considered the user experience from a tooling perspective and don't believe tooling will be impacted.
  • OR
  • I have considered the user experience from a tooling perspective and enumerated concerns in the summary.